Prev Next |
The type or namespace name '<*>' does not exist in the class or namespace '<*>' (are you missing an assembly reference?)
Could not find a part of the path 'c:\inetpub\wwwroot\app_config\<*>'.
Sitecore cannot be installed in a virtual directory or subdirectory; it must be configured as an IIS document root.
Could Not Load File or Assembly
Server Error in '/' Application.
Could not load file or assembly
System.IO.FileNotFoundException
This generally indicates that Visual Studio 2005 has deleted various assemblies from the project’s bin folder; see Visual Studio .NET 2005, specicially regarding configuration of the Copy Local property on assembly references. To correct the error, copy all missing files from the bin directory of the another Sitecore instance or the Sitecore installation media.
Windows XP “Server”
The implementation of IIS on Windows XP is limited to 5 concurrent HTTP connections. If a browser is configured to request more than two resources concurrently, if a single user is too active in too many browsers and/or if too many “clients” otherwise request resources simultaneously; additional requests result in HTTP error codes and chaos in the client as JavaScript, CSS, image, web service and other requests fail intermittently. Most browsers allow only two concurrent HTTP connections to any server but it is possible to modify this setting as described at http://support.microsoft.com/?kbid=282402. Upgrade to Windows 2003, reduce the number of clients and/or delete the registry values as specified by Microsoft.
WebForm_PostBackOptions is undefined
This message may occur if ASP.NET validators are used and /WebResource.axd is not present in IgnoreUrlPrefixes of web.config.
Critical Error: Data Store Unavailable
This message may indicate that CommunityServer has been installed but not configured; see installation materials for the demo site or the Forums Module.
Sharing Databases and/or Document Root
Multiple IIS web sites should never share a single document root file system and multiple Sitecore instances should never share databases except where the implications are well understood such as runtimes sharing web and extranet databases. See:
Server Application Unavailable
The web application you are attempting to access on this web server is currently unavailable. Please hit the "Refresh" button in your web browser to retry your request. Administrator Note: An error message detailing the cause of this specific request failure can be found in the application event log of the web server. Please review this log entry to discover what caused this error to occur.
This error message may indicate that web sites running different versions of ASP.NET (such as 1.1 and 2.0) are attempting to share an application pool. On Windows XP restarting IIS is likely to resolve this issue, though this may be attempted on other operating systems as well. On Windows 2000 or 2003, ensure application pools are configured correctly on the Home Directory tab of each website in IIS.
Prev Next